View MAX66100_4366307.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

general description the MAX66100 contains a 64-bit unique identifier (uid) and a 13.56mhz iso 15693 rf interface in a single chip. the uid is revealed during the inventory process. the MAX66100 supports all iso 15693-defined data rates, modulation indices, subcarrier modes, the select- ed state, application family identifier (afi), and data storage format identifier (dsfid). afi and dsfid are factory programmed with customer-supplied data. applications driver identification (fleet application) access control asset tracking features ? fully compliant with iso 15693 and iso 18000-3 mode 1 standard ? 13.56mhz ?khz carrier frequency ? 64-bit unique, factory-programmed uid ? supports afi and dsfid function ? write: 10% or 100% ask modulation using 1/4 (26kbps) or 1/256 (1.6kbps) pulse-position coding ? read: load modulation using manchester coding with 423khz and 484khz subcarrier in low (6.6kbps) or high (26kbps) data-rate mode ? compatible with existing iso 15693 products on the market ? powered entirely through the rf field ? operating temperature: -25? to +50? MAX66100 iso 15693-compliant 64-bit uid ________________________________________________________________ maxim integrated products 1 ordering information ic load switched load magnetic coupling antenna rx_in tx_out transmitter 13.56mhz reader MAX66100 typical operating circuit 19-5622; rev 0; 1/11 for pricing, delivery, and ordering information, please contact maxim direct at 1-888-629-4642, or visit maxim? website at www.maxim-ic.com. + denotes a lead(pb)-free/rohs-compliant package. part temp range pin-package MAX66100e-000aa+ -25c to +50c iso card MAX66100k-000aa+ -25c to +50c key fob mechanical drawings appear at end of data sheet. evaluation kit available
detailed description the MAX66100 contains a 64-bit unique identifier (uid) and a 13.56mhz iso 15693 rf interface in a single chip. the uid is accessed through standard iso 15693 function commands. the data rate can be as high as 26.69kbps. the MAX66100 supports afi and dsfid. applications of the MAX66100 include driver identification (fleet application), access control, and asset tracking. overview figure 1 shows the relationships between the major control and memory sections of the MAX66100. figure 2 shows the applicable iso 15693 commands and their purpose. the network function commands allow the master to identify all slaves in its range and to change their state, e.g., to select one for further com- munication. the protocol for these is described in the network function commands section. all data is read and written least significant bit (lsb) first, starting with the least significant byte (lsb). parasite power as a wireless device, the MAX66100 is not connected to any power source. it gets the energy for operation from the surrounding rf field, which must have a minimum strength as specified in the electrical characteristics table. unique identification number (uid) each MAX66100 contains a factory-programmed and locked identification number that is 64 bits long (figure 3). the lower 36 bits are the serial number of the chip. the next 8 bits store the device feature code, which is 01h. bits 45 to 48 are 0h. the code in bit locations 49 to 56 identifies the chip manufacturer, according to iso/iec 7816-6/am1. this code is 2bh for maxim. the code in the upper 8 bits is e0h. the uid is read accessible through the inventory and get system information commands. MAX66100 iso 15693-compliant 64-bit uid 2 _______________________________________________________________________________________ absolute maximum ratings electrical characteristics (t a = -25? to +50?.) (note 1) stresses beyond those listed under ?bsolute maximum ratings?may cause permanent damage to the device. these are stress rating s only, and functional operation of the device at these or any other conditions beyond those indicated in the operational sections of the specificatio ns is not implied. exposure to absolute maximum rating conditions for extended periods may affect device reliability. note 1: system requirement. note 2: production tested at 13.56mhz only. note 3: guaranteed by simulation; not production tested. note 4: measured from the time at which the incident field is present with strength greater than or equal to h (min) to the time at which the MAX66100? internal power-on reset signal is deasserted and the device is ready to receive a command frame. not characterized or production tested; guaranteed by simulation only. maximum incident magnetic field strength ..........141.5db?/m operating temperature range ...........................-25? to +50? relative humidity ..............................................(water resistant) storage temperature range ...............................-25? to +50? parameter symbol conditions min typ max units rf interface carrier frequency f c (notes 1, 2) 13.553 13.560 13.567 mhz at 25c, MAX66100e 110.5 activation field strength (note 3) h min at 25c, MAX66100k 122.0 dba/m maximum field strength h max at 25c (note 3) 137.5 dba/m power-up time t por (notes 3, 4) 1.0 ms rf front- end voltage regulator internal supply uid, afi, dsfid iso 15693 frame formatting and error detection f c data modulation figure 1. block diagram
MAX66100 iso 15693-compliant 64-bit uid _______________________________________________________________________________________ 3 available commands: data field affected: inventory stay quiet select reset to ready uid, afi, dsfid, administrative data uid uid uid network function commands get system information uid, afi, dsfid, constants memory function commands command type: MAX66100 figure 2. iso 15693 commands overview msb lsb 64 57 56 49 48 45 44 37 36 1 e0h 2bh 0h feature code (01h) 36-bit ic serial number figure 3. 64-bit uid sof 1 or more data bytes crc (lsb) crc (msb) eof time figure 4. iso 15693 frame format iso 15693 communication concept the communication between the master and the MAX66100 (slave) is based on the exchange of data packets. the master initiates every transaction; only one side (master or slaves) transmits information at any time. each data packet begins with a start-of-frame (sof) pattern and ends with an end-of-frame (eof) pattern. a data packet with at least 3 bytes between sof and eof is called a frame (figure 4). the last 2 bytes of an iso 15693 frame are an inverted 16-bit crc of the preceding data generated according to the crc-16-ccitt polynomial. this crc is transmitted with the lsb first. for more details on the crc-16-ccitt, refer to iso 15693 part 3, annex c. for transmission, the frame information is modulated on a carrier frequency, which is 13.56mhz for iso 15693. the subsequent paragraphs are a concise description of the required modulation and coding. for full details including graphics of the data coding schemes and sof/eof timing, refer to iso 15693-2, sections 7.2, 7.3, and 8. the path from master to slave uses amplitude modu- lation (figure 5); the modulation index can be either in the range of 10% to 30% or 100% (iso 15693-2, section 7.1). the standard defines two pulse-position coding schemes that must be supported by a compli- ant device. scheme a uses the ? out of 256?method (figure 6), where the transmission of 1 byte takes 4.833ms, equivalent to a data rate of 1655bps. the location of a modulation notch during the 4.833ms con- veys the value of the byte. scheme b uses the ? out of 4?method (figure 7), where the transmission of 2 bits takes 75.52?, equivalent to a data rate of 26,484bps. the location of a modulation notch during the 75.52? conveys the value of the 2 bits. a byte is transmitted as a concatenation of four 2-bit transmissions, with the least significant 2 bits of the byte being transmitted first. the transmission of the sof pattern takes the same time as transmitting 2 bits in scheme b. the sof pattern has two modulation notches, which makes it
MAX66100 distinct from any 2-bit pattern. the position of the sec- ond notch tells whether the frame uses the ? out of 256?or ? out of 4?coding scheme (figures 8 and 9, respectively). the transmission of the eof pattern takes 37.76?; the eof is the same for both coding schemes and has one modulation notch (figure 10). the path from slave to master uses one or two subcar- riers, as specified by the subcarrier_flag bit in the request data packet. the standard defines two data rates for the response, low (approximately 6600bps) and high (approximately 26,500bps). the data_rate_flag bit in the request data packet specifies the response data rate. the data rate varies slightly depending on the use of one or two subcarriers. the lsb is transmitted first. a compliant device must support both subcarrier modes and data rates. in the single subcarrier case, the subcarrier frequency is 423.75khz. one bit is transmitted in 37.76? (high data rate) or 151? (low data rate). the modulation is the on/off key. for a logic 0, the subcarrier is on during the first half of the bit transmission time and off for the second half. for a logic 1, the subcarrier is off during the first half of the bit transmission time and on for the second half. see figure 11 for more details. in the two subcarrier cases, the subcarrier frequencies are 423.75khz and 484.28khz. the bit duration is the same as in the single subcarrier case. the modulation is equivalent to binary fm. for a logic 0, the lower sub- carrier is on during the first half of the bit transmission time, switching to the higher subcarrier for the second half. for a logic 1, the higher subcarrier is on during the first half of the bit transmission time, switching to the lower subcarrier for the second half. see figure 12 for details. the transmission of the sof pattern takes the same time as transmitting 4 bits (approximately 151? at a high data rate or approximately 604? at a low data rate). the sof is distinct from any 4-bit data sequence. the eof pattern is equivalent to a sof being transmit- ted backwards. the exact duration of the sof and eof varies slightly depending on the use of one or two sub- carriers (see figures 13 and 14, respectively). iso 15693-compliant 64-bit uid 4 _______________________________________________________________________________________ figure 5. downlink modulation (e.g., approximately 100% amplitude modulation) carrier amplitude 100% t figure 6. downlink data coding (case ? out of 256? pulse- modulated carrier 01234 . . . . .2 2 5 ....... ........2 5 2 2 5 3 2 5 4 2 5 5 ..... ~ 9.44 s ~ 18.88 s ~ 4.833ms
MAX66100 iso 15693-compliant 64-bit uid _______________________________________________________________________________________ 5 figure 8. downlink sof for ? out of 256?coding (carrier not shown) ~ 9.44 s ~ 37.76 s ~ 37.76 s ~ 9.44 s figure 7. downlink data coding (case ? out of 4? (carrier not shown) pulse position ?00? pulse position ?01? (1 = lsb) pulse position ?10? (0 = lsb) pulse position ?11? ~ 9.44 s ~ 9.44 s ~ 9.44 s ~ 9.44 s ~ 9.44 s ~ 75.52 s ~ 75.52 s ~ 75.52 s ~ 75.52 s ~ 66.08 s ~ 28.32 s ~ 47.20 s
MAX66100 iso 15693-compliant 64-bit uid 6 _______________________________________________________________________________________ figure 9. downlink sof for ? out of 4?coding (carrier not shown) ~ 9.44 s ~ 37.76 s ~ 37.76 s ~ 9.44 s ~ 9.44 s figure 10. downlink eof (identical for both coding schemes) (carrier not shown) ~ 9.44 s ~ 37.76 s ~ 9.44 s figure 11. uplink coding, single subcarrier case (high data-rate timing) transmitting a zero 423.75khz, ~ 18.88 s ~ 18.88 s ~ 37.76 s transmitting a one 423.75khz, ~ 18.88 s ~ 18.88 s ~ 37.76 s
MAX66100 iso 15693-compliant 64-bit uid _______________________________________________________________________________________ 7 figure 12. uplink coding, two subcarriers case (high data-rate timing) transmitting a zero 484.28khz, ~ 18.58 s 423.75khz, ~ 18.88 s ~ 37.46 s transmitting a one 484.28khz, ~ 18.58 s 423.75khz, ~ 18.88 s ~ 37.46 s figure 13. uplink sof, single subcarrier case (high data-rate timing) 423.75khz 423.75khz ~ 56.64 s ~ 56.64 s ~ 37.76 s figure 14. uplink sof, two subcarriers case (high data-rate timing) 423.75khz 423.75khz 484.28khz 484.28khz ~ 55.75 s ~ 56.64 s ~ 37.46 s
MAX66100 iso 15693-compliant 64-bit uid 8 _______________________________________________________________________________________ iso 15693 slave states and address modes initially, the master has no information whether there are any rf devices in the field of its antenna. the master learns the uids of the slaves in its field from the responses to the inventory command, which does not use the address_flag and the select_flag bits. the state transitions are controlled by network function com- mands. figure 15 shows details. iso 15693 defines four states in which a slave can be plus three address modes. the states are power-off, ready, quiet, and selected. the address modes are nonaddressed, addressed, and selected. the addressed mode requires that the master include the slave? uid in the request, which increases the size of the requests by 8 bytes. table 1 shows which address mode is applicable depending on the slave? state and how to set the address_flag and the select_flag bits for each address mode. iso 15693 states and transitions power-off state this state applies if the slave is outside the master? rf field. a slave transitions to the power-off state when leaving the power-delivering rf field. when entering the rf field, the slave automatically transitions to the ready state. ready state in this state, a slave has enough power to perform any of its functions. the purpose of the ready state is to have the slave population ready to process the inventory command as well as other commands sent in the addressed or nonaddressed mode. a slave can exit the ready state and transition to the quiet or the selected state upon receiving the stay quiet or select command sent in the addressed mode. quiet state in this state, a slave has enough power to perform any of its functions. the purpose of the quiet state is to silence slaves that the master does not want to commu- nicate with. only commands sent with the addressed mode are accepted and processed. this way the mas- ter can use the nonaddressed mode for communication with remaining slaves in the ready state, which mini- mizes the size of the request data packets. as long as no additional slaves arrive in the rf field, it is safe for the master to continue communicating in the nonad- dressed mode. a slave can exit the quiet state and transition to the ready or the selected state upon receiv- ing the reset to ready or select command sent in the addressed mode. selected state in this state, a slave has enough power to perform any of its functions. the purpose of the selected state is to isolate the slave that the master wants to communicate with. commands are accepted and processed regard- less of the address mode in which they are sent, includ- ing the inventory command. with multiple slaves in the rf field, the master can put one slave in the selected state and leave all the others in the ready state. this method requires less communication than using the quiet state to single out the slave for communication. for a slave in the selected state, the master can use the selected mode, which keeps the request data packets as short as with the nonaddressed mode. a new slave entering the rf field cannot disturb the communication, since it stays in the ready state. a slave can exit the address modes slave states nonaddressed mode (address_flag = 0; select_flag = 0) addressed mode (address_flag = 1; select_flag = 0) selected mode (address_flag = 0; select_flag = 1) power-off (inactive) (inactive) (inactive) ready yes yes no quiet no yes no selected yes yes yes table 1. slave states and applicable address modes
selected state and transition to the ready or the quiet state upon receiving the reset to ready command sent in any address mode or the stay quiet command sent in the addressed mode. a slave also transitions from selected to ready upon receiving a select command if the uid in the request is different from the slave? own uid. in this case the master? intention is to transition another slave with the matching uid to the selected state. if the slave already in the selected state does not recognize the command (e.g., due to a bit error), two slaves could be in the selected state. to prevent this from happening, the master should use the reset to ready or the stay quiet command to transition a slave out of the selected state. MAX66100 iso 15693-compliant 64-bit uid _______________________________________________________________________________________ 9 figure 15. iso 15693 state transitions diagram power-off ready selected quiet in field note 1 note 3 out of field out of field reset to ready [n, a, s] out of field note 2 response legend: note 1: the slave processes the inventory command and other commands provided that they are sent in the [n] or [a] address mode. note 2: the slave processes only commands sent in the [a] address mode. note 3: the slave processes the inventory command and other commands in any address mode. response to reset to ready reset to ready [a] matching uid stay quiet [a] matching uid select [a], nonmatching uid response to select no response stay quiet [a] matching uid select [a] matching uid select [a] matching uid address mode legend: [n] nonaddressed [a] addressed [s] selected
MAX66100 request flags the command descriptions on the subsequent pages begin with a byte called request flags. the iso 15693 standard defines two formats for the request flags byte. the state of the inventory_flag bit controls the function of the bits in the upper half of the request flags byte. the function of the request flags byte is as follows. inventory_flag bit not set bits 8, 4: no function. these bits have no function. they must be transmitted as 0. bit 7: options flag (option_flag). this bit is used with block read commands to include the block security sta- tus in the response. if not applicable for a command, the option_flag bit must be 0. bit 6: address flag (address_flag). this bit specifies whether all slaves in the master? field that are in the selected or ready state process the request (bit = 0) or only the single slave whose uid is specified in the request (bit = 1). if the address_flag bit is 0, the request must not include a uid. the combination of both the select_flag and address_flag bits being set (= 1) is not valid. bit 5: select flag (select_flag). this bit specifies whether the request is processed only by the slave in the selected state (bit = 1) or by any slave according to the setting of the address_flag bit (bit = 0). bit 3: inventory flag (inventory_flag). this bit must be 1 for the inventory command only. for all other com- mands, this bit must be 0. bit 2: data rate flag (data_rate_flag). this bit speci- fies whether the response data packet is transmitted using the low data rate (bit = 0) or the high data rate (bit = 1). bit 1: subcarrier flag (subcarrier_flag). this bit specifies whether the response data packet is transmit- ted using a single subcarrier (bit = 0) or two subcarriers (bit = 1). inventory_flag bit set bits 8, 7, 4: no function. these bits have no function. they must be transmitted as 0. bit 6: slot counter flag (nb_slots_flag). this bit specifies whether the command is processed using a slot counter (bit = 0) or without using the slot counter (bit = 1). bit 5: application family identifier flag (afi_flag). to detect only slaves with a certain afi value, the afi_flag bit must be 1 and the desired afi value must be included in the request. if the least significant nibble of the afi in the request is 0000b, slaves process the command only if the most significant nibble of the afi matches. if the afi in the request is 00h, all slaves process the command regardless of their afi. bit 3: inventory flag (inventory_flag). this bit must be 1 for the inventory command only. for all other com- mands, this bit must be 0. bit 2: data rate flag (data_rate_flag). this bit speci- fies whether the response data packet is transmitted using the low data rate (bit = 0) or the high data rate (bit = 1). bit 1: subcarrier flag (subcarrier_flag). this bit specifies whether the response data packet is transmit- ted using a single subcarrier (bit = 0) or two subcarriers (bit = 1). iso 15693-compliant 64-bit uid 10 ______________________________________________________________________________________ bit 8 (msb) bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 (lsb) 0 option_flag address_flag select_flag 0 inventory_flag (= 0) data_rate_flag subcarrier_flag bit 8 (msb) bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 (lsb) 0 0 nb_slots_flag afi_flag 0 inventory_flag (= 1) data_rate_flag subcarrier_flag request flags, inventory_flag bit not set request flags, inventory_flag bit set
MAX66100 iso 15693-compliant 64-bit uid ______________________________________________________________________________________ 11 network function commands the command descriptions show the data fields of the request and response data packets. to create the com- plete frame, an sof, 16-bit crc, and eof must be added (see figure 4). the iso 15693 standard defines four network function commands: inventory, stay quiet, select, and reset to ready. this section describes the format of the request and response data packets. inventory the inventory command allows the master to learn the uids and dsfids of all slaves in its rf field in an itera- tive process. it is the only command for which the inventory_flag bit must be 1. the inventory command uses two command-specific parameters, which are the mask length and the mask pattern. the mask allows the master to preselect slaves for responding to the inventory command. the lsb of the mask aligns with the lsb of the slave? uid. the master can choose not to use a mask, in which case all slaves qualify, provid- ed they are not excluded by the afi criteria (see the request flags section). the maximum mask length is 60 (3ch, if nb_slots_flag = 0) or 64 (40h, if nb_slots_flag = 1). the mask pattern defines the least significant bits (as many as specified by the mask length) that a slave? uid must match to qualify for responding to the inventory command (case nb_slots_flag = 1). if the slot counter is used (nb_slots_flag = 0), the value of the slot counter extends the mask pattern at the higher bits for compari- son to the slave? uid. the slot counter starts at 0 after the inventory request frame is transmitted and incre- ments during the course of the inventory command with every subsequent eof sent by the master. the pro- cessing of an inventory command ends when the mas- ter sends the sof of a new frame. response data for the inventory command (no error) is transmitted only if a slave qualifies to respond. in case of an error in the request, slaves do not respond. when receiving the inventory command, the slave devices in the rf field enter the collision management sequence. if a slave meets the conditions to respond, it sends out a response data packet. if multiple slaves qualify, e.g., afi, mask, and slot counter are not used, the response frames collide and are not readable. to receive readable response frames with the uid and dsfid, the master must eliminate the collision. not knowing the slave population, the master could begin with a mask length of 0 and activate the slot counter. by using this method and going through all 16 slots, the master has a chance to receive clean responses (i.e., the slave is identified) as well as collid- ing responses. to prevent a slave that has been identi- fied from further participating in the collision management sequence, the master transitions it to the quiet state. next, the master issues another inventory command where the slot number that previously gener- ated a collision is now used as a 4-bit mask, and runs again through all 16 slots. if a collision is found, another inventory command is issued, this time with a mask that is extended at the higher bits by the slot counter value that produced the collision. this process is repeated until all slaves are identified. for a full description of the inventory command processing by the slave device and the timing specifications, refer to iso 15693 part 3, sections 8 and 9. request flags command afi (note 1) mask length mask pattern (note 2) (1 byte) 01h (1 byte) (1 byte) (up to 8 bytes) note 1: the afi byte is transmitted only if the afi_flag bit is set to 1. the afi byte, if transmitted, narrows the range of slaves tha t qualify for responding to the request. note 2: the mask pattern is transmitted only if the selection mask length is not 0. if the mask length is not an integer multiple of 8, the msb of the mask pattern must be padded with 0 bits. the lsb of the mask pattern is transmitted first. response flags dsfid uid 00h (1 byte) (8 bytes) request data for the inventory command response data for the inventory command (no error)
MAX66100 stay quiet the stay quiet command addresses an individual slave and transitions it to the quiet state. the request must be sent in the addressed mode (select_flag bit = 0, address_flag bit = 1). the slave transitioning to the quiet state does not send a response. select the select command addresses an individual slave and transitions it to the selected state. the request must be sent in the addressed mode (select_flag bit = 0, address_flag bit = 1). the slave transitioning to the selected state sends a response. if there was a slave with a different uid in the selected state, then that slave transitions to the ready state without sending a response. reset to ready the reset to ready command addresses an individual slave and transitions it to the ready state. to address a slave in the quiet state, the request must be sent in the addressed mode (select_flag bit = 0, address_flag bit = 1). to address a slave in the selected state, the request can be sent in any address mode. the slave transitioning to the ready state sends a response. memory function commands the command descriptions show the data fields of the request and response data packets. to create the com- plete frame, an sof, 16-bit crc, and eof must be added (see figure 4). iso 15693 defines three address modes, selected, addressed, and nonaddressed, which are specified through the setting of the select_flag bit and the address_flag bit. the memory function commands can be issued in any address mode. to access slaves in the quiet state, the addressed mode is required. the addressed mode requires that the master include the slave's uid in the request. error indication in case of an error, the response to a request begins with a response flags byte 01h followed by one error code. if there was no error, the response begins with a response flags byte 00h followed by command-specific data, as specified in the detailed command description. if the MAX66100 does not recognize a command, it does not generate a response. iso 15693-compliant 64-bit uid 12 ______________________________________________________________________________________ request flags command uid (1 byte) 02h (8 bytes) request flags command uid (1 byte) 25h (8 bytes) * if this command is processed without any error, the slave responds with a response flags byte of 00h. request flags command uid** (1 byte) 26h (8 bytes) * if this command is processed without any error, the slave responds with a response flags byte of 00h. ** the uid is transmitted only in the addressed mode. request data for the stay quiet command request data for the select command* request data for the reset to ready command*
MAX66100 iso 15693-compliant 64-bit uid ______________________________________________________________________________________ 13 detailed command descriptions in the request data graphics of this section, the uid field is shaded to indicate that the inclusion of the uid depends on the address mode. get system information the get system information command is the only com- mand beyond the network function level that the MAX66100 supports. it allows the master to retrieve technical information about the MAX66100. the ic ref- erence code indicates the die revision in hexadecimal format, such as a1h, a2h, b1h, etc. crc generation the iso 15693 standard uses a 16-bit crc, generated according to the crc-16-ccitt polynomial function: x 16 + x 12 + x 5 + 1 (see figure 16). this crc is used for error detection in request and response data pack- ets and is always communicated in the inverted form. after all data bytes are shifted into the crc generator, the state of the 16 flip-flops is parallel-copied to a shift register and shifted out for transmission with the lsb first. for more details on this crc, refer to iso/iec 15693-3, annex c. request flags command uid (1 byte) 2bh (8 bytes) response flags info flags uid dsfid afi number of blocks memory block size ic reference 00h 0fh (8 bytes) (1 byte) (1 byte) 00h 07h (1 byte) request data for the get system information command response data for the get system information command (no error) figure 16. crc-16-ccitt generator 1st stage msb lsb 2nd stage 7th stage 8th stage 6th stage x 0 x 1 3rd stage 4th stage 5th stage x 2 x 3 x 4 polynomial = x 16 + x 12 + x 5 + 1 input data x 5 x 6 11th stage x 11 9th stage 10th stage x 9 x 10 12th stage 15th stage 14th stage 13th stage x 12 x 13 x 14 x 7 16th stage x 16 x 15 x 8
MAX66100 iso 15693-compliant 64-bit uid 14 ______________________________________________________________________________________ command-specific iso 15693 communication protocol?egend symbol description gsy command get system information sof start of frame rqf request flags byte (always sent by master) crc-16 transmission of an inverted crc-16 (2 bytes) generated according to crc-16-ccitt eof end of frame rsf response flags byte (always sent by slave) [uid] the tags unique 8-byte identification number; could be sent by either the master or the slave. the brackets [ ] indicate that the transmission of the uid depends on the request flags (rqf). symbol description iflg info flags byte (always sent by slave) dsfid data storage format identifier byte afi application family identifier byte nblk number of blocks byte (slave memory size indicator) mbs memory block size byte (slave memory block size) icr ic reference byte (slave chip revision) command-specific iso 15693 communication protocol?olor codes iso 15693 communication examples master-to-slave slave-to-master sof sof eof uid afi icr mbs iflg nblk dsfid rsf = 00h rqf gsy eof (carrier) [uid] crc-16 get system information success crc-16
MAX66100 iso 15693-compliant 64-bit uid ______________________________________________________________________________________ 15 MAX66100k-000aa+ top view side view 54mm 28mm 7.7mm 1.6mm 85.60mm 53.98mm 0.76mm 14.29mm 3.49mm MAX66100e-000aa+ top view side view key fob iso card mechanical drawings
MAX66100 iso 15693-compliant 64-bit uid maxim cannot assume responsibility for use of any circuitry other than circuitry entirely embodied in a maxim product. no circu it patent licenses are implied. maxim reserves the right to change the circuitry and specifications without notice at any time. 16 ____________________maxim integrated products, 120 san gabriel drive, sunnyvale, ca 94086 408-737-7600 2011 maxim integrated products maxim is a registered trademark of maxim integrated products, inc. revision history revision number revision date description pages changed 0 1/11 initial release

▲Up To Search▲

Price & Availability of MAX66100

	To Download MAX66100 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .